Skip to content

Align Copilot formatting guidance with existing linting/formatting skill#7885

Closed
Copilot wants to merge 14 commits into
mainfrom
copilot/sub-pr-7884
Closed

Align Copilot formatting guidance with existing linting/formatting skill#7885
Copilot wants to merge 14 commits into
mainfrom
copilot/sub-pr-7884

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented May 14, 2026

This change is a standalone formatting-guide update.

It updates repository guidance for Copilot-driven changes to avoid duplicating formatting instructions already documented in the existing linting/formatting skill.

  • Formatting/CI guidance update

    • Removed duplicated step-by-step CMake remediation guidance from .github/copilot-instructions.md.
    • Kept guidance centralized via the existing Linting and formatting section and linked .github/skills/formatting-and-linting.md.
  • Scope

    • Documentation/instructions only (.github/copilot-instructions.md).
    • No production, test, or source code behavior changes.

Agent-Logs-Url: https://github.com/microsoft/CCF/sessions/fb2c3354-e196-424f-8e7a-9d52825c3668

Co-authored-by: maxtropets <16566519+maxtropets@users.noreply.github.com>
@maxtropets
Copy link
Copy Markdown
Collaborator

@copilot where are the changes?

@maxtropets maxtropets changed the title [WIP] [WIP] Remove stale cchost mentions across tests, samples, schema, and host config Remove stale cchost mentions across tests, samples, schema, and host config May 14, 2026
Copilot AI changed the title Remove stale cchost mentions across tests, samples, schema, and host config Clarify standalone merge target (main) for stale cchost cleanup PR May 14, 2026
Copilot AI requested a review from maxtropets May 14, 2026 13:05
Copy link
Copy Markdown
Contributor Author

Copilot AI commented May 14, 2026

@copilot where are the changes?

You’re right — there were no file changes before. I’ve now pushed 32fb0c5, which adds an explicit repo Copilot instruction to always run ./scripts/ci-checks.sh before pushing and to run ./scripts/cmake-format-checks.sh -f when CI reports a CMake format failure (no UI changes to screenshot).

@maxtropets maxtropets marked this pull request as ready for review May 14, 2026 13:22
@maxtropets maxtropets requested a review from a team as a code owner May 14, 2026 13:22
@maxtropets
Copy link
Copy Markdown
Collaborator

@copilot adjust PR description, don't mention ant other PR, it's just a standalone task for the formatting guide.

@maxtropets maxtropets changed the title Clarify standalone merge target (main) for stale cchost cleanup PR Ask copilot to format as per CI requirements in PRs May 14, 2026
@maxtropets maxtropets changed the base branch from copilot/sub-pr-7883 to main May 14, 2026 13:24
Copy link
Copy Markdown
Contributor Author

Copilot AI commented May 14, 2026

@copilot adjust PR description, don't mention ant other PR, it's just a standalone task for the formatting guide.

Updated the PR description to keep it strictly as a standalone formatting-guide task and removed references to other PRs. No code changes were needed for this update (HEAD: c191052; no UI changes).

Copilot AI changed the title Ask copilot to format as per CI requirements in PRs Update Copilot formatting guidance with CI checks and CMake auto-fix steps May 14, 2026
Comment thread .github/copilot-instructions.md Outdated
## Code changes

- `ci-checks.sh` must run successfully before any commit is pushed.
- Always run `./scripts/ci-checks.sh` in the same way as CI before pushing. If it reports `CMake format` failures, run `./scripts/cmake-format-checks.sh -f` and re-run `./scripts/ci-checks.sh` before committing.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have a whole skill for this here: https://github.com/microsoft/CCF/blob/main/.github/skills/formatting-and-linting.md, and we have a pointer to it here: https://github.com/microsoft/CCF/blob/main/.github/copilot-instructions.md#linting-and-formatting - surely we should at most point to this section, not repeat the content.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@copilot do it

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in 8fdeb8e: I removed the duplicated formatting/CMake remediation bullet from .github/copilot-instructions.md, so this now relies on the existing “Linting and formatting” section and linked formatting skill instead of repeating that content. No UI changes to screenshot.

@maxtropets
Copy link
Copy Markdown
Collaborator

@copilot this PR carries unnecesasry changes from the cchost removal, only formatting instructions should stay in this PR.

Copilot AI requested review from Copilot and removed request for Copilot May 15, 2026 12:58
Copilot AI changed the title Update Copilot formatting guidance with CI checks and CMake auto-fix steps Align Copilot formatting guidance with existing linting/formatting skill May 15, 2026
Copilot AI requested review from Copilot and removed request for Copilot May 15, 2026 13:03
Agent-Logs-Url: https://github.com/microsoft/CCF/sessions/78b42f5d-4459-4ddc-9130-509c14885e9e

Co-authored-by: maxtropets <16566519+maxtropets@users.noreply.github.com>
Copilot AI requested review from Copilot and removed request for Copilot May 15, 2026 13:04
Copy link
Copy Markdown
Contributor Author

Copilot AI commented May 15, 2026

@copilot this PR carries unnecesasry changes from the cchost removal, only formatting instructions should stay in this PR.

Done in a275802 (with follow-up cleanup in 86826bb): I removed the unrelated cchost-removal scope from this PR so it no longer carries those extra changes. No UI changes to screenshot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants